8 Over The Air Provisioning (OTAP) > 8.3 OTAP Parameters

8.3
There is a set of parameters that control the OTAP procedures. These parameters can either be set by AT command (AT^SJOTAP, refer to [1] during the production of the device, or by SM (see Section 8.4) during operation of the device in the field. None of the parameters, which are set by AT command, can be overwritten by SM.
•
JAD File URL: the location of the JAD file is used to install or update procedures. The JAD file needs to be located on the net (e.g. http://someserver.net/somefile.jad or http://192.168.1.2/somefile.jad ).
•
Application Directory: this is the directory where a new application (JAD and JAR file) is installed. The delete operation deletes this directory completely. When entering the appli­cation directory with AT^SJOTAP or a short message ensure that the path name is not ter­minated with a slash. For example, type "a:" or "a:/otap" rather than "a:/" or "a:/otap/". See examples provided in Chapter 6.
•
•
•
Bearer: the network bearer used to open the HTTP/TCP/IP connection, either GPRS or CSD.
•
•
•
•
•
NotifyURL: the URL to which results are posted. This parameter is only used when the MIDlet-Install-Notify attribute or MIDlet-Delete-Notify attribute is not present in descriptor.
There are parameters that can only be set by AT command:
•
Note: If a password set by AT command, all SMs must include this password
•
•
Hide HTTP authentication parameters (TC65 only): this allows to hide the http authentica­tion parameters in the at^sjotap read command and the otap tracer.
Hide HTTP authentica­tion parameters
The length of the string parameters in the AT command is limited (see Table 10), the length in the SM is only limited by the maximum SM length.
The minimum set of required parameters depends on the intended operation (see Table 10).
“optional/P” indicates that this parameter is only necessary when a POST result is desired.